Date: Mon, 3 Oct 94 04:30:03 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.Edu Reply-To: TCP-Group@UCSD.Edu Precedence: List Subject: TCP-Group Digest V94 #218 To: tcp-group-digest TCP-Group Digest Mon, 3 Oct 94 Volume 94 : Issue 218 Today's Topics: need wampes info Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Sun, 2 Oct 1994 09:02:13 +0059 (EDT) From: Glenn M Silverberg Subject: need wampes info On Sat, 1 Oct 1994, Robert E. Brose II wrote: > If possible, I'd like to get some help from some of the WAMPES users > out there. > > I can run WAMPES fine. I have it running in an X window running 3 radio > interfaces and a slip port looped backed into the unix box to connect > to the unix tcp/ip. > > The 2 changes I'd like to make are: > > 1) free up the serial ports used to loop the tcp into the unix box. > I've heard there is a way to do this with pty's but have seen no > examples. > > 2) run WAMPES in the background and then use cnet to access it. It would be > nice to simply startup WAMPES when the normal tcp starts up on the unix box > so that if the power goes down, when it comes back on, the machine comes > back up and brings the gateways back online. > I've tried the example in the doc, net /tcp/startup It goes into the bg as expected but the route to wampes through the > serial port appears dead, kind of like wampes is waiting for some kind of > keyboard I/O in it's multitasking loop (just a guess). > > Anyone have any ideas for me to try out? > > Thanks, Bob I've had no problems bringing wampus up with the startup example above. I am/have run wampus in a 386sx25 macine under Linux Slackware 2.0 with a ax25 port on 2mtrs. I don't touch the comport in my linux boot and only address it from wampus. the node is wa1oaj-1.ampr.org. I have another node on a slip line to a 386dx40 running slackware 2.0 and xwindows (8 meg ram) this is wa1oaj-2.ampr.org. The only way wa1oaj-2 can work into wa1oaj-1 is to telnet wa1oaj-1 and then run "cnet" (remotely). I too have seen the references to "just use a pty...." myself. we need someone to explain how. Has anyone any info on "pty" 73 Glenn ------------------------------------------------------------------- wa1oaj@wa1oaj-1.ampr.org AMPERnet / Glennsil@world.std.com INTERnet ------------------------------------------------------------------- ------------------------------ End of TCP-Group Digest V94 #218 ******************************